Very slow datetime parsing with invalid time zone information
Reported by Edgars Beigarts | August 24th, 2009 @ 12:39 PM
@@@ $ ruby ./outlook.rb
2009-08-17T13:30:00+03:00
2009-08-17T14:30:00+03:00
3.450000 0.040000 3.490000 ( 3.628539)
Comments and changes to this ticket
-
Rick DeNatale September 4th, 2009 @ 10:56 AM
- State changed from “new” to “open”
- Assigned user set to “Rick DeNatale”
Just noticed this.
Not sure how to approach, Microsoft Outlook apparently produces VTIMEZONES like this:
BEGIN:VTIMEZONE
TZID:FLE Standard Time
BEGIN:STANDARD
DTSTART:16010101T040000
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONESo they think that Eastern daylight saving time starts at January 1, at 2:00 am, and ends one hour later, but that's not the important part, they think that it's been this way since January 1, 1601.
This must have been initiated by some American native tribe since 1601 pre-dates permanent Western settlements in North America as far as I know.
The problem is that this requires RiCal to step through all those time zone changes to get to the event time, which is a bit expensive.
I'm not sure how to approach 'fixing' this.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A new icalendar data (RFC 2445) gem for Ruby which supports time zones and enumeration of occurrences
Edgars Beigarts
Rick DeNatale